Well, here it is! Finally, a .dvi driver for your HP DeskJet
printer that will work on 520ST and up.  This program was bsed upon code
from the University of Utah written by Nelson Beebe, and was modified by
someone at HP in Vancouver, WA to work on a machine with limited memory. 
It does this by splitting the page into slices, and processing the
slices as separate entities.  This gets around the large amount of
memory needed to process an entire page bitmap in memory at once. 

	Included are two versions of dvidsk.ttp.  One does the page in 3
strips, and is called dvidsk3.ttp.  The other takes 5 strips, and may
work better if you run out of memory using the dvidsk3.ttp vesion.  Once
you figure out which one of these will work on your configuration,
rename it dvidsk.ttp.  The 5 strip version should run on all systems,
but I recommend the 3 strip if it will work for you, because it runs
just a little bit faster than the 5 strip version. 
 
	John R.  Dunning (of JRD fame :-) ) compiled this up for me from
the source I got from the person at HP.  I had to take this code,
compare it to the DVIEPS.TTP code that JRD had done prieviously, and
make all the needed patches.  I then shipped the code to JRD and he
compiled them on his Mega4 using GCC. 
	
	To use this, you will need a set of font files.  If you are
unfamiliar with Latex and .dvi files in general, you will probably be
confused at this.  This is not intended to be a complete tutorial. 
Perhaps after I finish my Master's degree in December, I will sit down
and try to make a start to finish package on using LaTeX and this driver
and dvieps on the ST.  But that won't come for a few months!

	I use PK font files.  I have a set of them in a separate ARC
file called DSKFONTS.ARC.  They are basically 500K worth of 300pk and
some 329pk fonts, most all of the ones you would need for any document. 
You will need to dearc them, and then on your harddrive (DON'T even
think about running this on floppies!!) make a directory called \fonts. 
In this directory, make a separate directory for each font name as in
"\fonts\cmr10" and in this directory coply the file cmr10.300.  Rename
this file to "300pk" Repeat this for each of the font families.  Of
course, if it is a 360pk font, move it to its correct folder and rename
it "360PK" A sample directory of fonts might look like:

f:\fonts\cmr10\300pk
f:\fonts\cmr10\329pk
f:\fonts\cmr10\360pk
f:\fonts\cmex10\300pk
 ....

Once you have the fonts, you can run the program by placing dvidsk.ttp
in the root level of the disk partition with the fonts.  Your source
.dvi file should be there also.  If you want to move you fonts around,
there are several environment variables you can set.  I use Neodesk, so
I set them up there, but any command shell like gualam will let you
define environment variables. 
TEXFONTS=f:\fonts (this points to your font directory, you will need this if
                    your fonts are anywhere except in partition F: since this
                    is the expected location)
TEXINPUTS (the location of your .dvi file)

The only one you really need to wory with is the TEXFONTS usually.

Once all of this is done, invoke the program as
dvidsk.ttp -z -(other options) dvifilename
the options are:

-z directs output to the printer instead of a diskfile.  You will
	probably always want to use this, as disk files are humongous!!

-q supresses all of the mesages, and speeds things up a bit.  Omit this
	for the first few times you run it to get familiar with the way
	the program looks for the files it needs. 

-x 
-y override the magins set in you document when it was LaTeXed.  You
can specify these as "-y-0.75in"  this move the top margin UP 3/4 of an inch
                     "-y1.0mm" moves the top margin DOWN 1 millimeter
Play with these to get a better idea how they affect the output.

-d24 this will list every file the program tries to open.  This can be helpful
      for figuring out which fonts you are missing.  

	That should do it.  This program isn't as speedy a printing out
on a laser printer at school or work, but if you could afford a laser
printer, you wouldn't need this program anyway!

	Utah will be releasing their new improved version of the driver
family sometime in the future, and when they do, I will try and get it
ported over for us ST users.  It is basically the same as this one,
except it should offer support for some of the \special commands that we
don't have in this version.  If you are printing any figures that you
make using FIG and transfig, then they probably won't show up when you
print them with this driver.  The specials are used to make splined
drawings and for more complex figures than you can usually do in
straight LaTeX.